-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
br: Remove statement from closure to prevent concurrent operation during backup system table #29730
Conversation
…ions. Signed-off-by: joccau <zak.zhao@pingcap.com>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, maybe also add a test (with race enabled, this would be easy to be caught)?
/component br |
/sig migrate |
Need to cherry-pick 5.2.* in tidb Repo and 5.1.* in br repo |
/run-check_dev_2 |
Signed-off-by: joccau <zak.zhao@pingcap.com>
@joccau: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/run-integration-br-tests |
/run-integration-br-test |
1 similar comment
/run-integration-br-test |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 3ca590a
|
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.3 in PR #29774 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.2 in PR #29976 |
* cp tidb#27769 * cp tidb#30393 * cherry-pick pingcap/tidb#29730 to pass integration test * skip integration test br_log_restore * fix some integration tests
Signed-off-by: joccau zak.zhao@pingcap.com
What problem does this PR solve?
Issue Number: close #29710
Problem Summary:
Append the prefix
__TiDB_BR_Temporary_
into system databasemysql
multiply.It causes restore failed because of incorrect schema name
What is changed and how it works?
Check List
Tests
Backup system table before fix
[2021/11/12 14:30:15.438 +08:00] [INFO] [validate.go:78] ["checksum success"] [db=__TiDB_BR_Temporary___TiDB_BR_Temporary___TiDB_BR_Temporary_mysql] [table=person]
Backup and restore system table after fix
[2021/11/12 15:54:00.890 +08:00] [INFO] [validate.go:78] ["checksum success"] [db=__TiDB_BR_Temporary_mysql] [table=person]
[2021/11/12 16:12:22.328 +08:00] [INFO] [ddl.go:553] ["[ddl] start DDL job"] [job="ID:168, Type:rename table, State:none, SchemaState:queueing, SchemaID:3, TableID:123, RowCount:0, ArgLen:3, start time: 2021-11-12 16:12:22.229 +0800 CST, Err:<nil>, ErrCount:0, SnapshotVersion:0"] [query="RENAME TABLE
__tidb_br_temporary_mysql.
personTO
mysql.
person;"]
Release note